Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-user is "delegate-my-device">
    <p>It allows to delegate a device.</p>

    <h3>Inputs</h3>
    A JSON with these parameters:

    <dl class="message-properties">
        <dt>id
            <span class="property-type">string</span>
        </dt>
        <dd> the nome of the device (you MUST have the ownership of the device)</dd>
		<dt>contextbroker
            <span class="property-type">string</span>
        </dt>
        <dd> the contextbroker of the device</dd>
		<dt>kind
            <span class="property-type">string</span>
        </dt>
        <dd> Kind of delegation. You can choose between READ_ACCESS,READ_WRITE, MODIFY and WRITE_ONLY.
        <dt>usernamedelegated
            <span class="property-type">string</span>
        </dt>
        <dd> Username of the person to be delegated to view the device. It is recommended that you set one of the two delegations (user or group) 
        <dt>groupdelegated
            <span class="property-type">string</span>
        </dt>
        <dd> Group to be delegated to view the device. To delegate to a group, you must set cn=GROUP_NAME,ou=ORGANIZATION_NAME. It is recommended that you set one of the two delegations (user or group) 
    </dl>

    <p>An example of the JSON array filled with correct data for user delegation:</p>
    <pre>
{
"id": "nameDevice",
"usernamedelegated": "username",
"contextbroker": "contextbroker",
"kind": "READ_ACCESS"
}
    </pre>
	    <p>An example of the JSON array filled with correct data for group delegation:</p>
    <pre>
{
"id": "nameDevice",
"groupdelegated": "cn=GROUP_NAME,ou=ORGANIZATION_NAME",
"contextbroker": "contextbroker",
"kind": "READ_ACCESS"
}
    </pre>

    <h3>Outputs</h3>
    <dl class="message-properties">
        <dd> Returns an object containing the delegation</dd>
    </dl>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>